System Monitor¶

Services¶

A Service is designed to perform a specific function and works with other services to provide a fully functional Logpoint. If any services performs poorly, it can impact other dependent services, leading to issues in Logpoint’s functionalities. For that reason, it is essential for services to always function. Services lists all running services and their status. You can stop, start, or restart them if you need to.

Services¶

Starting Services

1. Click the Start Service () icon from Actions.

2. To start all the services, click START ALL.

Stopping Services

1. Click the Stop Service () icon from Actions.

2. To stop all the services, click STOP ALL.

Restarting Services

1. Click the Restart Service () icon from Actions.

2. To restart all the services, click RESTART ALL.

System Processes¶

It shows all the processes currently running on the operating system where Logpoint is installed. The process list shows users, memory used by processes, commands on run, and process ids.

You can reload the page by clicking Reload.

Network Stack¶

The Network Stacks are used in communication networks.

Routing Table¶

It displays the routes to particular network destinations.

Address Resolution Protocol (ARP) Table¶

A protocol for mapping an Internet Protocol address (IP address) to a physical machine address that is recognized in the local network. This item data lists all the connection status under this protocol.

Network Interface¶

Displays Logpoint’s network status. It shows the state of all active interfaces such as eth0, l0, he-ipv6, tun0, tun1 and tun10000.

Disk Usage¶

It displays the total file system disk usage. It lists available disk space, disk usage and location of the file system. By default, Logpoint generates disk notifications when disk usage reaches 80% and again when the disk usage reaches 90%. For more information, go to Disk Usage Notification.

When available disk space falls to less than 2 GB, Logpoint stops collecting or fetching any logs and resumes only when there is at least 4 GB of available space. When the available space for a partition containing a repo path is less than 250 MB, Logpoint stops storing log messages in that partition and generates an audit log specifying that there is insufficient disk space available to store logs. Logpoint resumes data storage when enough space is available.

SNMP Monitoring¶

SNMP (Simple Network Management Protocol) Monitoring is used to monitor the status of your Logpoint. You can use SNMP walk, a command to retrieve values from an SNMP-enabled device by querying all OIDs (Object Identifiers) under a specific base. OIDs are unique, hierarchically structured numbers that identify particular object and component on a device. They are represented as a series of numbers separated by periods.

Use the base OID 1.3.6.1.4.1.54322.1 and the community string to get a list of all the exposed OIDs and their corresponding details. You can also use enterprises.54322.1 as the base OID. The MIB file with the OIDs is on the Service Desk. Monitoring tools interpret OIDs using MIB files, and some OIDs must end with .0 to ensure proper data retrieval. Logpoint provides two OIDs to maintain consistency: one with .0 and one without. For example, 1.3.6.1.4.1.54322.1.1 and 1.3.6.1.4.1.54322.1.1.0 represent the normalizer’s last recorded messages per second.

To monitor Logpoint using SNMPwalk:

1. Go to Settings >> System Settings from the navigation bar and click System Settings.

2. Select SNMP and enable SNMPD Port.

3. Enter a Community String. Copy the passphrase to use it in the SNMPwalk command.

4. Run the following SNMPwalk Command

snmpwalk -v2c -c <Community String> <IP address of Logpoint>:161 <OID>

If data is not available for the OID, No Such Instance currently exists at this OID is displayed as an output. When running the command for the first time, you might get a request time out.

Logpoint exposes the following OIDs:

The OIDs for ZFS pool statistics, statistics for the log size in repos, and LUN status gives information for all the entities. To retrieve the information for a single one, add an extra number corresponding to the respective pool, repo, or LUN after the provided OID.

For example, you can use enterprises.54322.1.12.1 to retrieve the names of all the ZFS pools and enterprises.54322.1.12.1.1 to retrieve the name of the first ZFS pool.

Additionally, you can use the following default OIDs for a Linux-based system:

General Statistics

CPU load

Memory statistics

Disk statistics